<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
	<meta http-equiv="Content-Type" content="text/html;charset=UTF-8" />
    <style type="text/css">
        .center {
            margin-left: auto;
            margin-right: auto;
            width:70%;
            background-color:#e5eecc;
        }

        .floatpink {
            position:relative;
            float:right;
            width:300px;
            background-color:#e5aabb;
            z-index: 0;
        }

        .floatgreen {
            position:relative;
            float:right;
            width:400px;
            background-color:#e5eecc;
            z-index: -1;
        }

        .clear {
            clear:both;
        }
    </style>
	<title></title>
</head>
<body>

    <!-- <div class="center">
        <p>After 1983 and the BSD port of TCP/IP, the Unix and ARPANET cultures began to fuse together. This was a natural development once the communication links were in place, since both cultures were composed of the same kind of people (indeed, in a few but significant cases the same people). ARPANET hackers learned C and began to speak the jargon of pipes, filters, and shells; Unix programmers learned TCP/IP and started to call each other "hackers". The process of fusion was accelerated after the Project Jupiter cancellation in 1983 killed the PDP-10's future. By 1987 the two cultures had merged so completely that most hackers programmed in C and casually used slang terms that went back to the Tech Model Railroad Club of twenty-five years earlier.</p>
        <p>(In 1979 I was unusual in having strong ties to both the Unix and ARPANET cultures. In 1985 that was no longer unusual. By the time I expanded the old ARPANET Jargon File into the New Hacker's Dictionary [Raymond96] in 1991, the two cultures had effectively fused. The Jargon File, born on the ARPANET but revised on Usenet, aptly symbolized the merger.)</p>
        <p>But TCP/IP networking and slang were not the only things the post-1980 hacker culture inherited from its ARPANET roots. It also got Richard Stallman, and Stallman's moral crusade.</p>
    </div> -->
<div class="clear">
<p>text old line</p>
</div>
<div class="floatpink">
	<p>Though the term "open source" and the Open Source Definition were not invented until 1998, peer-review-intensive development of freely shared source code was a key feature of the Unix culture from its beginnings.</p>
	<p></p>
	<p>For its first ten years AT$line$T's original Unix, and its primary variant Berkeley Unix, were normally distributed with source code. This enabled most of the other good things that follow here.</p>
</div>
<!-- <div class="clear"></div> -->
<div class="floatgreen">
	<p>here the float right text</p>
    <p>This tip describes how to get the Vim source from the new Mercurial repository. It assumes that you know how to compile Vim once you have the source. Examples are for Linux but it shouldn't be hard to adapt them to whatever OS you're running on (provided of course that there exists a version of Mercurial that runs on your OS). Also, the examples are written for GNU make: in case of doubt, try replacing make by gmake everywhere. </p>
</div>
<div class="clear">
<p>text old line</p>
</div>
<p>using clear css:</p>
<div class="floatpink">
	<p>Though the term "open source" and the Open Source Definition were not invented until 1998, peer-review-intensive development of freely shared source code was a key feature of the Unix culture from its beginnings.</p>
	<p></p>
	<p>For its first ten years AT$line$T's original Unix, and its primary variant Berkeley Unix, were normally distributed with source code. This enabled most of the other good things that follow here.</p>
</div>
<div class="clear"></div>
<div class="floatgreen">
	<p>here the float right text</p>
    <p>This tip describes how to get the Vim source from the new Mercurial repository. It assumes that you know how to compile Vim once you have the source. Examples are for Linux but it shouldn't be hard to adapt them to whatever OS you're running on (provided of course that there exists a version of Mercurial that runs on your OS). Also, the examples are written for GNU make: in case of doubt, try replacing make by gmake everywhere. </p>
</div>
</body>
</html>
